This bug is to find a way to either resolve, or find a work-around for this issue. The problem is that when a dev does a push to try and has a cached base revision, but uses --rebuild the rebuild will only be applied to the new run.

This isn't a big issue because a developer can either retrigger the test from CompareView directly, or from the try run. We should at least add some documentation to explain this.

That said, if it doesn't become a bigger issue, we could look into adding a flag like --clear-cache, or --no-cache to clear/ignore the cached revisions.